Cloud native realization of distributed ran elements

ABSTRACT

Various embodiments are directed to methods, apparatus, systems and the like for managing distributed radio access network (RAN) elements within a network associated with a network core, wherein for each of a plurality of distributed RAN elements (DREs) within the network associated with the network core a respective virtualized proxy element is configured to communicate with the DRE and mirror each of a plurality of functional elements (FEs) associated with the DRE.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to wireless communicationssystems and related networks, and more particularly to mechanisms for

BACKGROUND

This section is intended to introduce the reader to various aspects ofart, which may be related to various aspects of the present inventionthat are described and/or claimed below. This discussion is believed tobe helpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentinvention. Accordingly, it should be understood that these statementsare to be read in this light, and not as admissions of prior art.

Fifth generation (5G) wireless access technology, known as New Radio(NR) as described/developed by the Third Generation Partnership Project(3GPP), is a Service-Based Architecture (SBA) where network functionsbased in the Control Plane are interconnected via a service messageinterface bus for exposing the 5G network capabilities within the CoreNetwork (“core” or “5G core”). The 5G core communicates with andcontrols deployed radio access network (RAN) nodes, each of which usesuse gNBs formed thereat to communicate with, and provide backhaulservices to, user equipment (UE) connected thereto (e.g., mobile phones,sensors, etc.).

In various radio network deployment environments, such as thoseconsistent with the O-RAN Alliance, each of the deployed RAN or O-RANradio units (RUs, e.g., eNBs, gNBs, etc.) within a network of a networkoperator performs various Radio Access Network (RAN) functions such asproviding backhaul services to user equipment (UE) connected thereto(mobile phones, sensors, etc.). The deployed RUs may have been procuredfrom one or multiple vendors, where each vendor may offer some uniquefunctionality, as well as a requirement that other vendor-specificequipment be used within the network to support RU functionality.

Some network architectures contemplate that each RAN RU from a specificvendor is connected to a RAN distributed unit (DU) from that vendor viaan O-RAN Fronthaul interface, and each RAN-DU from that vendor is inturn connected to a RAN centralized unit (CU) from that vendor via F1over DOCSIS and normal transport mechanisms. The RAN CUs (from anyvendor used by the network operator) are then coupled to the 5G core viaan NG interface. The RAN DU and RAN CU functions of a vendor may beimplemented using virtualized or container implementations asvirtualized distributed units (vDUs) and centralized units (vCUs). Infact, some network architectures contemplate that such vDUs and vCUs maybe implemented via physically proximate containers (e.g., at the samedata center or cloud-services provider), enabling direct F1communications therebetween (i.e., avoiding DOCSIS transport), mixingand matching of multiple vendor entities and so on.

While the above-described architecture is especially well suited tohighly centralized network management architectures, even in lesscentralized network management architectures the various deployed RANsare geographically remote from the network managementarchitecture/functions. As such, the currently contemplated networkmanagement architectures suffer from various performance issues.

SUMMARY

Various embodiments are directed to methods, apparatus, systems and thelike addressing practical limitations associated with virtualized radioaccess network (RAN) elements associated with a network core such as a3GPP 4G/LTE or 5G network core. The network core may be traditionallyimplemented (i.e., non-virtualized), or implemented in a partially orfully virtual and/or containerized manner to include 3GPP 4G/LTE or 5Gcore network elements instantiated at a cloud-native platform in anetwork. The network core, however implemented, is configured to managedistributed RAN elements (DRE) such as RAN distributed units (DUs), RANradio units (RUs), RAN centralized units (CUs) and the like via proxyelements created/operated at resources proximate or associated with thenetwork core and corresponding to the actual or physicaldistributed/deployed RAN elements.

One embodiment comprises a method of managing distributed radio accessnetwork (RAN) elements within a network associated with a network core,the method comprising: for each of a plurality of distributed RANelements (DREs) within the network associated with the network core,configuring a respective virtualized proxy element to communicate withthe DRE and mirror each of a plurality of functional elements (FEs)associated with the DRE. In various embodiments the network corecomprises a virtualized network core implemented via processingresources and non-transitory memory resources, the processing resourcesconfigured to execute software instructions stored in the non-transitorymemory resources to provide thereby network core functions.

Additional objects, advantages, and novel features of the invention willbe set forth in part in the description which follows, and will becomeapparent to those skilled in the art upon examination of the followingor may be learned by practice of the invention. The objects andadvantages of the invention may be realized and attained by means of theinstrumentalities and combinations particularly pointed out in theappended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments of the presentinvention and, together with a general description of the inventiongiven above, and the detailed description of the embodiments givenbelow, serve to explain the principles of the present invention.

FIG. 1 depicts a simplified representation of a network servicesarchitecture useful in understanding the embodiments; and

FIG. 2 depicts a flow diagram of a method of managing distributed radioaccess network elements according to an embodiment.

It should be understood that the appended drawings are not necessarilyto scale, presenting a somewhat simplified representation of variousfeatures illustrative of the basic principles of the invention. Thespecific design features of the sequence of operations as disclosedherein, including, for example, specific dimensions, orientations,locations, and shapes of various illustrated components, will bedetermined in part by the particular intended application and useenvironment. Certain features of the illustrated embodiments have beenenlarged or distorted relative to others to facilitate visualization andclear understanding. In particular, thin features may be thickened, forexample, for clarity or illustration.

DETAILED DESCRIPTION

The following description and drawings merely illustrate the principlesof the invention. It will thus be appreciated that those skilled in theart will be able to devise various arrangements that, although notexplicitly described or shown herein, embody the principles of theinvention and are included within its scope. Furthermore, all examplesrecited herein are principally intended expressly to be only forpedagogical purposes to aid the reader in understanding the principlesof the invention and the concepts contributed by the inventor(s) tofurthering the art, and are to be construed as being without limitationto such specifically recited examples and conditions. Additionally, theterm, “or,” as used herein, refers to a non-exclusive or, unlessotherwise indicated (e.g., “or else” or “or in the alternative”). Also,the various embodiments described herein are not necessarily mutuallyexclusive, as some embodiments can be combined with one or more otherembodiments to form new embodiments.

The numerous innovative teachings of the present application will bedescribed with particular reference to the presently preferred exemplaryembodiments. However, it should be understood that this class ofembodiments provides only a few examples of the many advantageous usesof the innovative teachings herein. In general, statements made in thespecification of the present application do not necessarily limit any ofthe various claimed inventions. Moreover, some statements may apply tosome inventive features but not to others. Those skilled in the art andinformed by the teachings herein will realize that the invention is alsoapplicable to various other technical areas or embodiments.

Various embodiments are directed to methods, apparatus, systems and thelike addressing practical limitations associated with virtualized radioaccess network (RAN) elements associated with a network core such as a3GPP 4G/LTE or 5G network core. The network core may be traditionallyimplemented (i.e., non-virtualized), or implemented in a partially orfully virtual and/or containerized manner to include 3GPP 4G/LTE or 5Gcore network elements instantiated at a cloud-native platform in anetwork. The network core, however implemented, is configured to managedistributed RAN elements (DRE) such as RAN distributed units (DUs), RANradio units (RUs), RAN centralized units (CUs) and the like via proxyelements created/operated at resources proximate or associated with thenetwork core and corresponding to the actual or physicaldistributed/deployed RAN elements.

Various embodiments are directed to methods, apparatus, systems and thelike wherein 5G core network nodes within a virtualized network coreprovide services to distributed radio access network (RAN) elements(DREs) such as gNBs, RAN radio units (RUs), RAN distributed units (DUs)and the like via respective proxies instantiated at or proximate anetwork core, such as a virtualized network core. The specificfeatures/capability of the RAN elements may be accessed by, for example,an operation, administration and maintenance (OAM) system or functioncooperating with various network core functions, wherein the OAM systemin response to receiving a scanned bar code, quick response (QR) code,or other DRE identification (e.g., DRE identification code or labelaffixed to the DRE that may be scanned via a mobile device camera andthen transmitted to the network core by the mobile device such as via alocal or web-enabled setup application executed at the mobile device) sothat a relevant proxy may be allocated/instantiated and then used toautomatically provision the DRE.

FIG. 1 depicts a simplified representation of a network servicesarchitecture useful in understanding the embodiments. Specifically, FIG.1 depicts one or more data centers 110 comprising compute resources110-C(e.g., processing resources such as provided by one or moreservers, processors and/or virtualized processing elements or othercompute resources), memory resources 110-M (e.g., non-transitory memoryresources such as one or more storage devices, memories and/orvirtualized memory elements or storage resources), input/output (I/O)and network interface resources 110-NI, and other hardware resourcesand/or combined hardware and software resources suitable for use inimplementing a plurality of virtualized network management elements suchas described herein. Various other types of virtualized servicesplatforms, servers, and other known systems may be used to implement thevirtualized network management elements such as described herein. Thecompute or processing resources may also be configured to executesoftware instructions stored in the non-transitory memory resources toprovide thereby other network functions (NFs) as described herein

As depicted in FIG. 1 , the compute 110-C, memory 110-M, I/O and networkinterface 110-NI and other resources (not shown) of the data center(s)110 are used to instantiate a plurality of virtualized networkmanagement elements including, illustratively, a 5G core network 111, anoperation, administration and maintenance (OAM) system 112, and a proxymanager 113. As previously noted, while FIG. 1 depicts an architectureusing virtualized network management elements the various embodimentsmay also be use within the context of non-virtualized network managementelements and/or a combination of virtualized network management elementsand non-virtualized network management elements.

In the embodiment of FIG. 1 , the instantiated virtualized networkmanagement elements further include several virtualized networkmanagement elements substantially conforming to those defined by theOpen Radio Access Network (O-RAN) Alliance; namely, a RAN IntelligentController (MC) 115 and a Central Unit (CU) 114.

Generally speaking, the O-RAN Alliance contemplates an architecturewherein each of a plurality of RAN radio units (RUs) within a group ofRUs communicates with a RAN distributed unit (DU), and each of theRAN-DUs communicates with a RAN centralized unit (CU) which is in turncoupled a network core (e.g., 4G/LTE or 5G network core). An O-RANintelligent controller (MC) in communication with the DUs, CUs and corenetwork enables interoperability across different hardware and softwarecomponents in the O-RAN architecture, supporting various networkfunctions, services optimization, and the like.

As depicted in FIG. 1 . A strand-mounted small cell comprising a pair ofphysical devices 150 is installed at a location remote from that of thedata center(s) 110, but in communication with the data center(s) 110 viaa private RAN network 120, illustratively a 5G network comprisingnumerous radio units such as eNBs, gNBs, and supporting equipmentforming a 5G network managed by the 5G core 111.

The physical devices 150 comprise distributed radio access network (RAN)elements (DREs), illustratively, a RAN distributed unit (DU) 150-1 and aRAN radio unit (RU) 150-2. As depicted, the RAN DU 150-1 is operablycoupled to the private RAN network 120 and to the RAN RU 150-2. The RANRU 150-2 provides wireless network services to user equipment (UE) 105such as mobile phones, computers, sensors and other internet of things(IoT) devices and so on. The RAN DU 150-1 supports backhaul services tothe RAN RU 150-2 in support of the wireless network services providedthereby to, illustratively, UE 105.

As depicted in FIG. 1 , each of the RAN DU 150-1 and RAN RU 150-2 arecommunicatively coupled to respective proxies 116 instantiated at thedata center(s) 110; namely, RAN DU proxy 116-1 and RAN RU proxy 116-2.The proxies 116 are managed by the proxy manager 113 in response tooperational details provided by the OAM 112 and/or other managemententities. For example, the proxy manager 113 may create or instantiate aproxy 116 in response to information received from the OAM 112indicative of the discovery of a newly connected (or initialized) DU,RU, or other element communicating with or supporting the operations ofthe private RAN network 120.

The DRE 150 may comprise resources using licensed spectrum, unlicensedspectrum such as citizens broadband radio service (CBRS) spectrum, or acombination of licensed and unlicensed spectrum. The DRE 150 may, invarious embodiments, include mid-band (e.g., 3.5 GHz) gNBs, low-band(e.g., under 1 GHz) gNBs, or a combination of mid-band and low-bandgNBs. In the case of DRE 150 having Citizens Broadband Radio ServiceDevice (CBSD) capability, allocations of CBRS spectrum are provided viaa Spectrum Access System (SAS) (not shown).

Generally speaking, the various embodiments contemplate that thefunctions of a distributed RAN element (DRE) such as a gNB, RU, DU,and/or other DRE that are best implemented as embedded, high-performancefunctions using specific hardware/software, are implemented in thismanner rather than instantiated at a data center. In particular, thevarious embodiments contemplate a cloud-native (virtualized)implementation of substantially all 4G/LTE/5G network core functions,wherein high performance functions otherwise poorly supported by avirtualized implementation are implemented as respective virtualizedproxies invoked to cooperate with the preferred hardware/software of theDRE actually implementing the high performance function.

Various functions depicted and described herein may be implemented atthe elements or portions thereof as hardware or a combination ofsoftware and hardware, such as by using a general purpose computer, oneor more application specific integrated circuits (ASIC), or any otherhardware equivalents or combinations thereof. In various embodiments,computer instructions associated with a function of an element orportion thereof are loaded into a respective memory and executed by arespective processor to implement the respective functions as discussedherein. Thus various functions, elements and/or modules describedherein, or portions thereof, may be implemented as a computer programproduct wherein computer instructions, when processed by a computingdevice, adapt the operation of the computing device such that themethods or techniques described herein are invoked or otherwiseprovided. Instructions for invoking the inventive methods may be storedin tangible and non-transitory computer readable medium such as fixed orremovable media or memory, or stored within a memory within a computingdevice operating according to the instructions.

Various embodiments contemplate some or all of three main components;namely, (1) the creation and operation of proxy elements in thecloud-native environment, (2) the use of gNB, RU, DU, and/or otherdistributed RAN element (DRE) proxies to instantiate and operatecorresponding physical/distributed RU, DU, and/or other elements, and(3) continuous, real-time performance optimization ofphysical/distributed elements via the cloud based proxies.

FIG. 2 depicts a flow diagram of a method of managing distributed radioaccess network elements according to an embodiment. As previously noted,FIG. 1 primarily depicts an architecture using virtualized networkmanagement elements the various embodiments may also be use within thecontext of non-virtualized network management elements and/or acombination of virtualized network management elements andnon-virtualized network management elements. Similarly, FIG. 2 depicts amethod suitable for use with within the context of non-virtualizednetwork management elements and/or a combination of virtualized networkmanagement elements and non-virtualized network management elements

At step 210, for a distributed RAN element (DRE) to be managed if aproxy does not currently exist then a new proxy is instantiated andcommunication between the DRE and its proxy is established. For example,proxies 116-1 and 116-2 are associated with and in communication withrespective DRE 150-1 and 150-2. Referring to box 215, the DRE may benewly discovered, such as via a received bar code, quick response (QRcode or other DRE identifier, or via a database update, or by some othermechanism. In any event, however the DRE becomes known to, or discoveredby, the various management entities, an existing or new proxy isassociated with that DRE and configured to communicate with that DRE.

At step 220, the virtualized proxy associated with the DRE is configuredto mirror some or all of functional elements (FEs) associated with theDRE. Referring to box 225, such FEs may comprise, illustratively but notexhaustively, Cell ID, DRE configuration parameters or operatingparameters, DRE Operational state, DRE neighbor node(s) information andrelationships, DRE security parameters, DRE performance metrics, DRE OAMinformation, DRE traffic and/or other application programming interface(API) information, DRE capability information, and/or other information.

Generally speaking, the OAM system detects that a new DRE is present (orabsent) and uses proxy management function to create/destroy proxiesassociated with certain elements. For example, in response to receivinga scanned QR code of a distributed RAN element (DRE) such as via UE 105scanning the installed but not yet operational devices DU 150-1 or RU150-2, the OAM 112 may responsively generate the relevant proxy orproxies within the virtualized environment to represent the physicaldevices (e.g., distributed RAN elements) associated with the QR code.For example, the UE 105 may comprise any mobile device executing a via alocal or web-enabled DRE setup application configured to use camera orother optical input capability to scan a QR cod or other DREidentification code or label affixed to the DRE, and then use networkconnectivity capability to transmit the scanned DRE identificationinformation and any ancillary information (e.g., location information,local network information, subscriber information, etc.) to the networkcore or OAM system.

In various embodiments, the DRE identification information and ancillaryinformation effectively enable the OAM 112 to fully identify the DRE interms of its capability, the relevant subscriber location and billinginformation, the DRE capability information, the local networkconfiguration, and the like. The OAM 112 may retrieve relevant DREconfiguration information, system information, subscriber informationand the like to ensure that the generated proxy or proxies have all theinformation necessary to completely provision the DRE and, therefore,enable a zero-touch provisioning of the DRE in response to the QR code.This zero-touch provisioning or activation process may also be providedin response to a non-QR identifier, or by an update to a preconfigureddatabase (e.g., mapping states/functions/preference to this DRE) orother process. The Proxy Manager 113 manages the proxies, includingdefining/enabling responses to bar codes, QR codes, IP addresses, etc.,assigning an ID to the proxies, assigning network parameters for theproxies, establishing communication links from the proxies to corenetwork functions, and from the proxies to the distributed RAN elements(DREs).

For example, the creation of proxy elements as non-virtualized elements,virtualized elements, cloud-native virtualized elements, and the likethat mirror all the functional elements (FEs) of the physicalimplementation of the 5G high performance function, such as a physicalDU+Radio (e.g., Cell ID, RAN parameters, operational State, Neighborrelations, Security parameters, performance metrics, O&M and TrafficAPIs). The proxy element resides in the virtualized network cloud or aseparate cloud and is instantiated by the entry of a new network elementin the management database (e.g., a proxy manager 13 or orchestratorproxy) or a QR code scan of a physical entity. The proxy element can becreated before or after physical connectivity to the remote elementimplementing the 5G high performance function. A secure connection isestablished between the Proxy and the Physical DU (or physicalimplementation of some other 5G high performance function).

As step 230, each DRE is controlled/operated via its respective proxy,wherein FE changes from the network core or other management entitiessent to the proxy are communicated by the proxy to the respective DRE,and FE changes sent from the DRE to the proxy are communicated by theproxy to the network core or other management entity by the proxy.

Generally speaking, the proxy manager 113 (or orchestrator proxy)provides all the necessary information to the DRE via the proxy,including the initial provisioning of the DRE via the proxy. Whencomplete, the DRE is transitioned (via the relevant proxy) to anoperational mode from a provisioning mode.

For example, the use of the “DU Proxy” 116-1 to instantiate and operatethe actual physical distributed DU 150-1 and associated Radio(s). Themanagement system (Proxy Orchestrator/Proxy Manager entity) instantiatesthe proxies. The proxies communicate with each other to determine allthe relevant FEs that each new proxy needs to turn up and operate whenbeing integrated to the network (same mechanism as in a non-cloud-nativenetwork, but communication is done through the cloud platform and ismuch easier to coordinate and manage). The proxy then transmits the FEsto the physical DU. The physical DU and RU comes online with zero-touchprovisioning.

At step 240, DRE operation is monitored and the operation of individualDRE and the DRE population is optimized by one or more relevantmanagement entities.

For example, the use of continuous, real-time performance optimizationof physical/distributed elements by the cloud based proxies. Themanagement system (Proxy Orchestrator/Proxy Manager entity) may beconfigured to enable inter-proxy peer-to-peer links between DU proxies.Communications may be Real-time or Event Based, and may be customized bythe network operator, or implemented via ML. The management system(e.g., via the proxy manager 113) determines the optimal changes to FEsthat need to be implemented on the respective proxies. This may beachieved through inter-working and coordination with other cloud-basednetwork elements such as CU, RIC, and the like. The proxies 116 thentransfer any changes to the physical DUs 150 via the secure links andthe like. The proxies 116 may also have the ability to determine thelocal network level traffic based resource allocations of the physicalDUs, and determine the optimal local resource allocations of thephysical DUs so as to save energy, reduce interference, and maximizeperformance of the distributed RAN elements.

Various modifications may be made to the systems, methods, apparatus,mechanisms, techniques and portions thereof described herein withrespect to the various figures, such modifications being contemplated asbeing within the scope of the invention. For example, while a specificorder of steps or arrangement of functional elements is presented in thevarious embodiments described herein, various other orders/arrangementsof steps or functional elements may be utilized within the context ofthe various embodiments. Further, while modifications to embodiments maybe discussed individually, various embodiments may use multiplemodifications contemporaneously or in sequence, compound modificationsand the like. It will be appreciated that the term “or” as used hereinrefers to a non-exclusive “or,” unless otherwise indicated (e.g., use of“or else” or “or in the alternative”).

Although various embodiments which incorporate the teachings of thepresent invention have been shown and described in detail herein, thoseskilled in the art can readily devise many other varied embodiments thatstill incorporate these teachings. Thus, while the foregoing is directedto various embodiments of the present invention, other and furtherembodiments of the invention may be devised without departing from thebasic scope thereof.

1. A method managing distributed radio access network (RAN) elementswithin a network associated with a network core, the method comprising:for each of a plurality of distributed RAN elements (DREs) within thenetwork associated with the network core, configuring a respectivevirtualized proxy element to communicate with the DRE and mirror each ofa plurality of functional elements (FEs) associated with the DRE.
 2. Themethod of claim 1, wherein the network core comprises a virtualizednetwork core implemented via processing resources and non-transitorymemory resources, the processing resources configured to executesoftware instructions stored in the non-transitory memory resources toprovide thereby network core functions.
 3. The method of claim 1,wherein the FEs associated with the DRE comprise at least one of a CellID, RAN parameters, operational state, neighbor node relationships,security parameters, and performance metrics.
 4. The method of claim 1,wherein the FEs associated with the DRE further comprise at least one ofO&M information and traffic APIs.
 5. The method of claim 1, wherein theplurality of DREs comprise at least one RAN distributed unit (DU)configured to communicate via its respective virtual proxy element withthe network core.
 6. The method of claim 2, wherein the plurality ofDREs comprise at least one RAN distributed unit (DU) configured tocommunicate via its respective virtual proxy element with a virtualizedRAN centralized unit (CU).
 7. The method of claim 1, wherein theplurality of DREs comprise at least one RAN radio unit (RU) configuredto communicate via its respective virtual proxy element with the networkcore.
 8. The method of claim 2, wherein the plurality of DREs compriseat least one RAN radio unit (RU) configured to communicate via itsrespective virtual proxy element with a virtualized RAN distributed unit(DU).
 9. The method of claim 8, wherein the virtualized RAN distributedunit (DU) is configured to communicate with a virtualized RANcentralized unit (CU).
 10. The method of claim 1, further comprising: inresponse to network core discovery of a DRE within the networkassociated with the network core, instantiating the respectivevirtualized proxy element for the discovered DRE.
 11. The method ofclaim 10, wherein network core discovery of a DRE comprises receivinginformation including a scanned identifier associated with the DRE froma remote device proximate the DRE, and provisioning the DRE inaccordance with the received DRE information.
 12. The method of claim11, wherein the scanned identifier comprises a QR code associated withthe DRE.
 13. The method of claim 11, wherein the information associatedwith the DRE includes at least one of location information, localnetwork information, and subscriber information.
 14. The method of claim1, further comprising: in response to entry of a new DRE in a managementdatabase, instantiating the respective virtualized proxy element for theDRE.
 15. The method of claim 2, wherein the proxy element is implementedusing the processing and non-transitory memory resources common to thoseused to implement the network core.
 16. The method of claim 2, whereinthe proxy element is implemented using the processing and non-transitorymemory resources separate from those used to implement the network core.17. Apparatus configured to implement network functions at a networkcore, the apparatus comprising a processor configured to executeinstructions stored within a tangible computer readable medium toperform a method of managing distributed radio access network (RAN)elements within a network associated with the network core, the methodcomprising: for each of a plurality of distributed RAN elements (DREs)within the network associated with the network core, configuring arespective virtualized proxy element to communicate with the DRE andmirror each of a plurality of functional elements (FEs) associated withthe DRE.
 18. Network equipment used to implement network functions at anetwork core, the network equipment comprising a processor andnon-transitory memory, the processor configured to execute softwareinstructions stored in the non-transitory memory to provide thereby amethod managing distributed radio access network (RAN) elements within anetwork associated with the network core, the network equipmentconfigured to: for each of a plurality of distributed RAN elements(DREs) within the network associated with the network core, configuringa respective virtualized proxy element to communicate with the DRE andmirror each of a plurality of functional elements (FEs) associated withthe DRE.
 19. The network equipment of claim 18, wherein the networkequipment comprises an operation, administration and maintenance (OAM)system configured to cooperate with the network core.
 20. The networkequipment of claim 18, wherein the network core comprises a virtualizednetwork core implemented via processor and non-transitory memory, theprocessor configured to execute software instructions stored in thenon-transitory memory to provide thereby network core functions.